I tried without success to "Send-As" from my main mailbox user (main_user) as another user (alt_user). I did setup the permissions as follow: 1. Add-MailboxPermission alt_user user main_user accessright fullaccess inheritanceType all;2. Add-ADPermission main_user user alt_user AccessRights extendedright ExtendedRight send-as; For info, my main receive receptor config is :[MSH] C:\Documents and Settings\Administrator>get-receiveconnector "Client EXCHANGE" | flSchema : Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnectorSchemaAuthMechanism : Tls, BasicAuth, ExchangeServerBanner :BinaryMimeEnabled : TrueBindings : {0.0.0.0:25, 0.0.0.0:587}ChunkingEnabled : TrueDefaultDomain :DeliveryStatusNotificationEnabled : TrueEightBitMimeEnabled : TrueEnhancedStatusCodesEnabled : TrueExternallySecuredAsPartnerDomain :Fqdn : mail.mydomain.comComment :Enabled : TrueConnectionTimeout : 00:10:00ConnectionInactivityTimeout : 00:05:00MessageRateLimit : 600MaxInboundConnection : 5000MaxInboundConnectionPerSource : 100MaxInboundConnectionPercentagePerSource : 2MaxHeaderSize : 64KBMaxHopCount : 30MaxLocalHopCount : 3MaxLogonFailures : 3MaxMessageSize : 10MBMaxProtocolErrors : 5MaxRecipientsPerMessage : 200PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers, CustomPipeliningEnabled : TrueProtocolLoggingLevel : NoneRemoteIPRanges : {0.0.0.0-255.255.255.255}RequireEHLODomain : FalseRequireTLS : FalseServer : EXCHANGE_SERVERSizeEnabled : TrueTarpitInterval : 00:00:05AdminDisplayName :ObjectCategoryName : msExchSmtpReceiveConnectorExchangeVersion : 0.1 (8.0.535.0)CurrentObjectVersion : 0.1 (8.0.535.0)Name : Client EXCHANGEDistinguishedName : xxxxxxxxxxx....Identity : EXCHANGE\Client EXCHANGEGuid : xxxxxxxxxxx....ObjectCategory : xxxxxxxxxxx....ObjectClass : {top, msExchSmtpReceiveConnector}OriginalId : EXCHANGE\Client EXCHANGEWhenChanged : 11/6/2006 9:34:16 PMWhenCreated : 10/10/2006 2:25:36 AMObjectState : UnchangedOriginatingServer : xxxxxxxxxxx....IsReadOnly : FalseId : EXCHANGE\Client EXCHANGEIsValid : TruePlease help!

I set the Add-ADPermission ... -ExtendedRights Receive-As to the Mailbox Store and have exact the same problem. Get-ADPermission gives back: Identity User Deny Rights-------- ---- ---- ------WS03R2EEEXCHLCS\F... CONTOSO\OOF False Send-AsWS03R2EEEXCHLCS\F... CONTOSO\OOF False Receive-As Everything works fine on each mailbox except "Send-As". Is there anything more to do? Thank you, Josef

To use Active Directory Users and Computers to grant a user "Send as" permissions for another user's mailbox 1. On a computer that is running Exchange, click Start, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers. 2. In Active Directory Users and Computers, on the View menu, click Advanced Features. 3. Expand the domain node, and then click Users. 4. In the details pane, right-click the user for which you want to grant the Send as permission, and then click Properties. 5. In <User> Properties, on the Security tab, click Advanced. 6. In Advanced Security Settings for <User>, click Add. 7. In the Enter the object name to select box, type the name of the mailbox user or the group to which you want to grant Send as permissions, and then click Check Name to verify the user or group. Click OK. 8. In Permission Entry for <User>, in the Apply onto list, select This object only. 9. In the Permissions list, locate Send As, and then select the Allow check box. 10. Click OK to close the dialog boxes. To use the Exchange Management Shell to grant a user "Send as" permissions for another user's mailbox 1. Run the following command:Add-ADPermission "Mailbox" User "Domain\User" Extendedrights SendAs http://www.microsoft.com/technet/prodtechnol/exchange/e2k7help/5b67866c-d466-4200-a438-d1adf01482f0.mspx marcel01 wrote:I tried without success to "Send-As" from my main mailbox user (main_user) as another user (alt_user). I did setup the permissions as follow: 1. Add-MailboxPermission alt_user user main_user accessright fullaccess inheritanceType all;2. Add-ADPermission main_user user alt_user AccessRights extendedright ExtendedRight send-as; For info, my main receive receptor config is :[MSH] C:\Documents and Settings\Administrator>get-receiveconnector "Client EXCHANGE" | flSchema : Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnectorSchemaAuthMechanism : Tls, BasicAuth, ExchangeServerBanner :BinaryMimeEnabled : TrueBindings : {0.0.0.0:25, 0.0.0.0:587}ChunkingEnabled : TrueDefaultDomain :DeliveryStatusNotificationEnabled : TrueEightBitMimeEnabled : TrueEnhancedStatusCodesEnabled : TrueExternallySecuredAsPartnerDomain :Fqdn : mail.mydomain.comComment :Enabled : TrueConnectionTimeout : 00:10:00ConnectionInactivityTimeout : 00:05:00MessageRateLimit : 600MaxInboundConnection : 5000MaxInboundConnectionPerSource : 100MaxInboundConnectionPercentagePerSource : 2MaxHeaderSize : 64KBMaxHopCount : 30MaxLocalHopCount : 3MaxLogonFailures : 3MaxMessageSize : 10MBMaxProtocolErrors : 5MaxRecipientsPerMessage : 200PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers, CustomPipeliningEnabled : TrueProtocolLoggingLevel : NoneRemoteIPRanges : {0.0.0.0-255.255.255.255}RequireEHLODomain : FalseRequireTLS : FalseServer : EXCHANGE_SERVERSizeEnabled : TrueTarpitInterval : 00:00:05AdminDisplayName :ObjectCategoryName : msExchSmtpReceiveConnectorExchangeVersion : 0.1 (8.0.535.0)CurrentObjectVersion : 0.1 (8.0.535.0)Name : Client EXCHANGEDistinguishedName : xxxxxxxxxxx....Identity : EXCHANGE\Client EXCHANGEGuid : xxxxxxxxxxx....ObjectCategory : xxxxxxxxxxx....ObjectClass : {top, msExchSmtpReceiveConnector}OriginalId : EXCHANGE\Client EXCHANGEWhenChanged : 11/6/2006 9:34:16 PMWhenCreated : 10/10/2006 2:25:36 AMObjectState : UnchangedOriginatingServer : xxxxxxxxxxx....IsReadOnly : FalseId : EXCHANGE\Client EXCHANGEIsValid : TruePlease help!

I have done this: http://www.microsoft.com/technet/prodtechnol/exchange/e2k7help/5b67866c-d466-4200-a438-d1adf01482f0.mspx But i am still not able to "send as"

There are two mailbox one is call "Allen" other is "Jacob" and Domain Name is MSFT. Now Allen want to access Jacob mailbox(Jacob want delegate his mailbox to Allen),my step is: Add-ADPermission -Identity "Jacob" -User "MSFT\Allen" -ExtendedRights Send-As Add-MailboxPermissiona "Jacob" -User "MSFT\Allen" -AccessRights FullAccess Add-ADPermission -Identity "Jacob" -User "MSFT\Allen" -ExtendedRights Receive-As Modify Allen Outlook Profile in advance tab Add Jacob mailbox now Allen can access Jacob mailbox and reply email and sender will show Allen

That is a great answer that actually doesn't work for the problem with Exchange 2007. Issue - Cannot "Send As" so that the From field is actually just the User2 name, not User1 On Behalf of User2 The FullAccess right exists. The SendAs right exists. Outlook still complains that User1 cannot "send on behalf" of User2.

I am experiencing exactly the same problem on Exchange 2007. User A's mailbox has the Send-As and Full-Access permission allowed for UserB, so that User B should be able to send as (USER A). However User B's Outlook reports that User B doesn't have send on behalf of permissions for User A. Of coursegranting Send on Behalf, will not produce the required result.... Any ideas? Thanks, James

The only way I have gotten this to work correctly is if User B, modifies his email profile in Outlook so that USER A's mailbox is the primary mailbox on Exchange that User B is connecting to. Then under the properties/advanced/ add additional mail box, add User B's own mailbox, so they both show up in the view. Of course any new email messages will show as being from USER A by default, which is usually not the desired effect (requires user to modify the "from" field). With this all being said, it would NOT appear to be permissions related. I hope this is something that will be addressed in the form of a patch/fix for either Exchange 2007 or Outlook (2003 or 2007) where ever the problem really is. Thanks, James.

I found this post trying to figure out my "Send-as" problem that was like below. I was getting an "unable to send on behalf of...." but the user had Send-As permissions & Full Access permissions. Here's what I found... I was mis-reading the error... I did not have rights to "send on behalf of", which is different than "send-as". Eventually found this post over the the Exchange Team Blog..... Scenario: Configure mailbox permissions Permission settings are advanced user cases which are available only at the shell command line, except "Send on behalf" permission which can be granted in the console (in the Mail Flow Setting tab of the mailbox property pages). Shell one-liner: # Grant "Send on behalf" permissionSet-Mailbox testmbx -GrantSendOnBehalfTo jaredz # Grant "Send-As" permissionAdd-ADPermission testmbx -ExtendedRights Send-As -user jaredz # Grant full mailbox access permissionAdd-MailboxPermission testmbx -AccessRights FullAccess -user jaredz Once I did the first line (I had already done two & three) everything worked like a champ. Here's my scenario... I have an Exchange 2007 server at my house, I have created multiple "users" for the different email addresses I have to keep things separated. I have Outlook save the credientials of "user1" to access all of the other mailboxes and Outlook prompts me for the profile to load. This way I am not prompted for the credentials (my laptop is NOT a member of the domain) for each profile. marcel01 wrote: I tried without success to "Send-As" from my main mailbox user (main_user) as another user (alt_user). I did setup the permissions as follow: 1. Add-MailboxPermission alt_user user main_user accessright fullaccess inheritanceType all;2. Add-ADPermission main_user user alt_user AccessRights extendedright ExtendedRight send-as; Please help!

I had a somewhat related problem last week. I need the ability to log in to other users' mailboxes. None of the suggestions I found online would work. I finally pieced an answer together and put my answer here:http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1526425&SiteID=17I just tested it on your problem doing a "Send As" and it appears to work fine. Note, though, that this solution will grant you Send As permission on every single mailbox in the database. If that's not what you want, steer clear of this solution.Max.

Now here's what I don't understand. Why do we need both Send-on-Behalf and Send-As? I want to sendas another user without it saying the message was sent on behalf of another user. As others said, with just the SendAs permission, when I use the From: you get an error back saying you need Send on Behalf permission. How can I send with just the SendAs and make it appear that it came from another account without it saying the message was sent on behalf of another user?

Ok - I suspect that many people complaining of this problem have done a double upgrade of Exchange (5.5 -> 2003 -> 2007 for us). Here is the scenario I was in, and what caused my issues: We started with the following setup: 1 Exchange 5.5 Server located on our "main site"1 Remote Office - External "domain" that is not in our forest - a badly configured setup yes - but inherited. So mailbox for COMPANYHQ\userA , being accessed and used by MINISITE\userA The issues for us, I thought, was based on the "Send-As" permission - it was not. Although the Outlook clients where responding with "No permission to Send As / Send of Behalf of" messages. a) Upon migrating from 5.5 to 2003 we had to add in the "SELF" account as an associated externalaccount to get them to migrate properly. b) We then had to configure accounts on the remote site to have Send-As permissions so that they could send e-mails (off the top of my head it was something to do with Outlook attempting to use its local authenticated to send the mail). We did this and it all was working fine. We decomissioned the 5.5 server, and all was on 2003. We then setup Exchange 2007 running alongside the 2003 server. Migrating users who were part of our COMPANYHQ domain caused no issues. They all worked perfectly. The migrated users on the MINISITE domain however didn't work. They could open and view their mailboxes - however they said they did not have permission to send.Now here is my mistake - remembering the 2003 migration I quickly went off to find out how to grant these permissions to the account again - except this time it made no difference. It still did not work. Not matter what the remote site always claimed it didn't have permission. The key was the type of mailbox it is - it needs to be a "Linked Mailbox". Upon migrating all my MINISITE users were coming across as "Shared Mailboxes". Now this probably isn't the only way to do this - I imagine you can do this with the PowerShell but here is what we did to correct the issue (remember this will probably ONLY occur if you migrated from 5.5 to 2003 (and hence put in the SELF account in as "Associated External Account")). 1) Migrate all MINISITE mailboxes (so the COMPANYHQ\userA mailbox which MINISITE\userA will access) back on to the old 2003 server2) Using active directory go to the user.3) Under "Exchange Advanced" go to "Mailbox Rights"4) Delete the "SELF" account (or if you are worried about it being there, remove its "Associated external account" permission)5) Select the MINISITE\userA user and assign them "Associated External Account" (and we gave "Full Mailbox Access" as well)6) Re-Migrate the mailbox back on to the Exchange 2007 server7) Check that the Exchange Manager shows the mailbox type as "Linked Mailbox". The account should then work as when it was on the 2003 server. Final note - we found that we had to Reboot Vista clients to get them to be able to successfully work (without a reboot they didn't give an error but sat at the "Send/Recieve" window). XP Clients however we could just close and reopen Outlook. Hope this helps those people complaining of the above problem - but that the advice given everywhere just doesn't work. Took us a long day of frantic troubleshooting to get to the bottom of it!

I've still got the same problem... Isn't there anybody from MS that can look in to this issue? tried every link/suggestion but still not able to "send as" Grtz Tall1

This is of no help.. But I thought I would post it. Every Admin that I know that used to have 5.5, and then went to 2000/2003 a few years ago and now to 2007 has had send as issues with 2007. I know a lot of at least 10 separate issues with 10 outcomes. This is going to be an ongoing issue that will most likely not get completely "fixed" until a service Pack. In contrast, every admin that I talk to that started out on Exchange 2003, and went to 2007 has had no issues. Like I said.. No help. But I just wanted to throw it out there since this is a veryfustrating issue.

I posted earlier with some questions in regards getting Send As and Send on Behalf to work. I figured I would post an update with everything I have learned. I created an entry in my blog that teaches exactly how you can get Send As to work as well as Send on Behalf using several different methods and some issues that might prevent it from working. http://www.shudnow.net/2007/08/12/send-on-behalf-and-send-as/Hope this helps.

Hello All, I was recently (August 2007) setting up a mail enabled public folder that I wanted people to be able to 'Send As' from. I followed the standard instructions for adding 'Send As' permissions for a user found here: http://technet.microsoft.com/en-us/library/aa998291.aspx Then I couldn't find how, in Outlook 2007, does a user actually change the "From:' field of an email. That solution can be found here: http://www.msexchange.org/tutorials/Sending-As.html The above link also provides useful information about how long it can actually take for the 'Send As' permission to propagate through the system and actually takingeffect(could be up to 2 hours but can be sped up by restarting the Exchange Information Store). After following the instructions in the above links dutifully I still couldn't 'Send As' and was getting the lack of permission error. Finally I did Set-MailPublicFolder -Identity <MailPublicFolderIdParameter> -HiddenFromAddressListsEnabled $False and that fixed the problem. Just to verify that was really the problem I set it to $True again and couldn't 'Send As' again. Set it back to $False and it works! Hope this helps! Yves www.mqual.com

I can send on behalf of but I cannot send as anyone. The only way I have found to send as is to be member of Domain Admins, so it's a bad solution for the rest of users.

AEMPerth wrote: Has anyone had success with "Send As" and distribution lists? I've set up the AD permissions and replication has taken place. The only thing I have not done is restart the Exchange store... I can see the PowerShell scripts to configure a user to "send as" for another user/mailbox, but nothing about distribution lists Cheers Andrew Yes it work for me. But nothing special, just by adding the "send as" right to theSELF "group" The users members of this group can send message as my distribution group. I don't have the time to test this with an user account but i would be work

It did end up working using only the AD permsissions...just took along time to replicate, even after I forced AD replication.

Hello, I have created my own post but will add my comments to this post.... Why would you have to restart the store for it to work because when you add them to the domain admins it works straight away, this also applies to the send on behalf of via the delivery options in the exchange console..... The "Send As" stopped working when we ran the legacypermissions switch while prepping our domain for Exchange 2007. I read somewhere (sorry forgotten where) that in Exchange 2000 send as worked fine but users complained that it was far to easy for users to send as if they have full access to a mailbox, so MS removed this function for anyone with full access to a mailbox for Exchange 2003 and Exchange 2007. I agree with one of the previous posts as to why can't MS sort this out... Why should I log a call for such a simple issue as this is very important to our users?!?!?! Paul

Our issue has been reoslved by chekcing the 'admincount' of the user from within adsiedit it has to be set to 0 and not 1 Paul

Thank you, it worked like a charm.

Thank you, I have the same problem With a new and clean 2007SP1 config. adding permission with "Set-Mailbox "hostuser" -GrantSendOnBehalfTo "guestuser" resolve the problem. Thank you for your tip

My issue was just time see this comment from the following link:http://www.msexchange.org/tutorials/Sending-As.htmlHowever, its important to note that it can take a while, possibly up to two hours, for the permissions changes to take effect which has proved to be the source of much frustration amongst Exchange administrators.Once the permissions changes have been made and the Outlook From field completed, its quite common for the assistant to receive a non-delivery report just after sending the message.Of course, the key wording above is the line that reads You do not have permission to send to this recipient.Is it possible to speed up this permissions change process?Well, I havent been able to get someone from Microsoft to confirm this, but I believe its possible via the Mailbox Cache Age Limit registry key documented in KB article 327378. The KB article mentions changing the Mailbox Cache Age Limit registry key, which according to the article is used to re-read logon quota information.In my experience, modifying this key (or creating it if it doesnt exist) with a suitable value, in minutes, speeds up the permissions change process.Note that you must restart the Information Store service after modifying this registry key.The general consensus of opinion here is not to make this value too low; a sensible value is 15 minutes. The alternative to creating or modifying this registry key is to simply re-start the Information Store service, which appears to make the permissions changes take effect immediately.Of course, restarting the Information Store service is rarely practical during business hours and you may also not prefer to go poking around in the registry, so you can also choose to wait for the permissions to be re-read at the next interval, which, as stated earlier, could be up to 2 hours.->brian

... along a similar line, here's the scenario:UserA in DomainA has a contact record in DomainBThere isa DL in DomainB that UserA wants the ability to Send As.Is it possible to have the contact record for UserA in DomainB to be granted Send As rights to that DL?If UserA has a user account created in DomainB, and that DomainB\UserA account is granted Send As rights for the DL, would this work?DomainA and DomainB have a two-way trust configured.->Kenny

Scenario: Configure mailbox permissions Permission settings are advanced user cases which are available only at the shell command line, except "Send on behalf" permission which can be granted in the console (in the Mail Flow Setting tab of the mailbox property pages). Shell one-liner: # Grant "Send on behalf" permissionSet-Mailbox testmbx -GrantSendOnBehalfTo jaredz # Grant "Send-As" permissionAdd-ADPermission testmbx -ExtendedRights Send-As -user jaredz # Grant full mailbox access permissionAdd-MailboxPermission testmbx -AccessRights FullAccess -user jaredz Once I did the first line (I had already done two & three) everything worked like a champ. Thanks fixed my issue also. Also only had to do line one as two and three were done.

Sorry, hit the wrong link, did not mean to propose as answer, meant to answer! :) If your dist list is called Test123 and the user that wants to SendAs the dist list is named Andrew, then the cmdlet would be: Set-DistributionGroup -Identity Test123 -GrantSendOnBehalfTo Andrew Worked for me. mrRaintree Solutions, LLC

Thank you so very kindly.I used Send-As wizard in Exchange 2007 and then immediately tried it. It did not work and sent back emails to me stating that I didn't have permission.I didn't want to wait 2 hours for things to propagate so I tried your suggestion of restarting the Microsoft Exchange Information Store...IT WORKED PERFECTLY! I was now able to send as that user and it tested perfectly!Thank you!Your friend in Virginia,Paul L.

I found that the exchange object must be a "Shared Mailbox" for "Send As" to work. Powershell command: C:\>Set-Mailbox helpdesk -Type:Shared

I have read so many posts about this issue and there are a few fixes some good ones listed above. However my issue goes unresolved..... My scenario I have 1 mail user accessing their single mail box (no problems here). Although I need to give other non mail users access to this same mailbox? The below solution seems to depend on all the users being mail users! # Grant "Send on behalf" permission Set-Mailbox testmbx -GrantSendOnBehalfTo jaredz # Grant "Send-As" permission Add-ADPermission testmbx -ExtendedRights Send-As -user jaredz # Grant full mailbox access permission Add-MailboxPermission testmbx -AccessRights FullAccess -user jaredz regards

After much searching i found this http://knicksmith.blogspot.com/2007/03/exchange-2007-and-shared-mailboxes.html it is instuctions on creating "shared mailboxes" which do not reliy on the user being a mail user so i can configure multiple non mail users to access a single mailbox. I could not get the PS code to work for adding the send as permission so I did this thorugh the exchange admin console which worked just fine. hope this helps...

I found this post trying to figure out my "Send-as" problem that was like below. I was getting an "unable to send on behalf of...." but the user had Send-As permissions & Full Access permissions. Here's what I found... I was mis-reading the error... I did not have rights to "send on behalf of", which is different than "send-as". Eventually found this post over the the Exchange Team Blog..... Scenario: Configure mailbox permissions Permission settings are advanced user cases which are available only at the shell command line, except "Send on behalf" permission which can be granted in the console (in the Mail Flow Setting tab of the mailbox property pages). Shell one-liner: # Grant "Send on behalf" permission Set-Mailbox testmbx -GrantSendOnBehalfTo jaredz # Grant "Send-As" permission Add-ADPermission testmbx -ExtendedRights Send-As -user jaredz # Grant full mailbox access permission Add-MailboxPermission testmbx -AccessRights FullAccess -user jaredz Once I did the first line (I had already done two & three) everything worked like a champ. I'm having the same problem, but the users have been migrated to another domain. Exchange still resides in the old domain (for now). I have been unable to grant SendOnBehalfTo an external user in another domain. Is this possible? The odd thing about it is, two users who have been migrated worked out of the box. Two others, not.